Skip to content

Conversation

@JamesC1305
Copy link

Create a new github workflow to monitor releases daily from the libseccomp repository. When a new release is detected, lodge an issue against the Firecracker repo.

Changes

  • Create new Dockerfile environment variable for Libseccomp version to be pulled
  • Create new daily Github Action that:
    • Reads the environment variable to determine current libseccomp version
    • Checks for new releases
    • Compares semantic version to ensure latest release is applicable
    • Checks for an existing "update libseccomp" issue, and if not:
    • Creates an issue against Firecracker repo telling us to update

Reason

To notify us when there is a new libseccomp version to consume

License Acceptance

By submitting this pull request, I confirm that my contribution is made under
the terms of the Apache 2.0 license. For more information on following Developer
Certificate of Origin and signing off your commits, please check
CONTRIBUTING.md.

PR Checklist

  • I have read and understand CONTRIBUTING.md.
  • I have run tools/devtool checkbuild --all to verify that the PR passes
    build checks on all supported architectures.
  • I have run tools/devtool checkstyle to verify that the PR passes the
    automated style checks.
  • I have described what is done in these changes, why they are needed, and
    how they are solving the problem in a clear and encompassing way.
  • I have updated any relevant documentation (both in code and in the docs)
    in the PR.
  • I have mentioned all user-facing changes in CHANGELOG.md.
  • If a specific issue led to this PR, this PR closes the issue.
  • When making API changes, I have followed the
    Runbook for Firecracker API changes.
  • I have tested all new and changed functionalities in unit tests and/or
    integration tests.
  • I have linked an issue to every new TODO.

  • This functionality cannot be added in rust-vmm.

@JamesC1305 JamesC1305 force-pushed the libseccomp-update-workflow branch from bb8e940 to 1f3278b Compare November 21, 2025 10:14
Create a new github workflow to monitor releases daily from the
libseccomp repository. When a new release is detected, lodge an issue
against the Firecracker repo.

Signed-off-by: James Curtis <[email protected]>
@JamesC1305 JamesC1305 force-pushed the libseccomp-update-workflow branch from 1f3278b to 5a89e70 Compare November 21, 2025 10:17
@codecov
Copy link

codecov bot commented Nov 21, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 82.87%. Comparing base (fa2627a) to head (5a89e70).

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #5525   +/-   ##
=======================================
  Coverage   82.87%   82.87%           
=======================================
  Files         270      270           
  Lines       27780    27780           
=======================================
  Hits        23024    23024           
  Misses       4756     4756           
Flag Coverage Δ
5.10-m5n.metal 83.06% <ø> (ø)
5.10-m6a.metal 82.33% <ø> (+<0.01%) ⬆️
5.10-m6g.metal 79.63% <ø> (-0.01%) ⬇️
5.10-m6i.metal 83.06% <ø> (ø)
5.10-m7a.metal-48xl 82.32% <ø> (ø)
5.10-m7g.metal 79.63% <ø> (-0.01%) ⬇️
5.10-m7i.metal-24xl 83.02% <ø> (ø)
5.10-m7i.metal-48xl 83.03% <ø> (+<0.01%) ⬆️
5.10-m8g.metal-24xl 79.63% <ø> (-0.01%) ⬇️
5.10-m8g.metal-48xl 79.63% <ø> (ø)
6.1-m5n.metal 83.09% <ø> (+<0.01%) ⬆️
6.1-m6a.metal 82.36% <ø> (ø)
6.1-m6g.metal 79.63% <ø> (ø)
6.1-m6i.metal 83.08% <ø> (ø)
6.1-m7a.metal-48xl 82.35% <ø> (ø)
6.1-m7g.metal 79.63% <ø> (-0.01%) ⬇️
6.1-m7i.metal-24xl 83.09% <ø> (ø)
6.1-m7i.metal-48xl 83.10% <ø> (+<0.01%) ⬆️
6.1-m8g.metal-24xl 79.63% <ø> (-0.01%) ⬇️
6.1-m8g.metal-48xl 79.63% <ø> (+<0.01%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant